An intended use case is to find regression tests that need to be adapted when a loss of coverage in some files is observed when a new feature is merged.

For example, when improving the constant propagator to propagate more operations, some existing tests that were intended to test the constraint encoding of those operations might then be solved via constant propagation. Thus, the existing tests need to be adapted to use non-constants as inputs.

• Each commit message has a non-empty body, explaining why the change was made.
• Methods or procedures I have added are documented, following the guidelines provided in CODING_STANDARD.md.
• The feature or user visible behaviour I have added or modified has been documented in the User Guide in doc/cprover-manual/
• Regression or unit tests are included, or existing tests cover the modified code (in this case I have detailed which ones those are in the commit message).
• n/a My commit message includes data points confirming performance improvements (if claimed).
• My PR is restricted to a single feature or bugfix.
• n/a White-space or formatting changes outside the feature-related changed lines are in commits of their own.